chore: remove concurrency call and pin action version to have a base run before action v4#57
Merged
GuillaumeLagrange merged 1 commit intomainfrom Sep 19, 2025
Merged
Conversation
CodSpeed WallTime Performance ReportMerging #57 will not alter performanceComparing Summary
|
CodSpeed Instrumentation Performance ReportMerging #57 will not alter performanceComparing Summary
|
b2c109e to
07d97aa
Compare
559865e to
545ce50
Compare
v3 was the action version of the previous base job. We want to do changes one by one, and v4 (current main) does not work without the concurrency change. This just brings the concurrency change that we will need to set the action version to the latest (v4) again.
545ce50 to
102e9c1
Compare
art049
approved these changes
Sep 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For better traceability, we pin the action to v3, which was the previous base run version, and then we make the changes that are necessary for v4 to work.
In a subsequent PR, we'll bump the action to v4, to isolate the effects of each change and have better visibility